| Package | hl7.terminology |
| Type | CodeSystem |
| Id | Id |
| FHIR Version | R5 |
| Source | http://terminology.hl7.org/https://build.fhir.org/ig/HL7/UTG/CodeSystem-v3-refSeq.html |
| Url | http://www.ncbi.nlm.nih.gov/refseq |
| Version | 2.0.1 |
| Status | retired |
| Date | 2021-11-09T10:00:00+10:00 |
| Name | RefSeq |
| Title | Gene Reference Sequence Collection |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | The Reference Sequence (RefSeq) is one of the NCBI projects, the RefSeq collection aims to provide a comprehensive, integrated, non-redundant, well-annotated set of sequences, including genomic DNA, transcripts, and proteins. ReqSeq is accessible via BLAST, Entrez, and the NCBI FTP site. Information is also available in Entrez Genomes and Entrez Gene, and for some genomes additional information is available in the Map Viewer. RefSeq entries can be used with the HL7 coded data type. For example, in the HL7 messages specified according to the HL7 V2 Clinical Genomics Fully LOINC-Qualified Genetic Variation Model, RefSeq entries can be used to as the observation values for genomic reference sequence identifiers (LOINC \#: 48013-7). More information may be found at: http://www.ncbi.nlm.nih.gov/RefSeq Versioning informaiton: The latest release of RefSeq was released on May 13, 2009 with the release number of 35. RefSeq generates new releases roughly every two months. The dates of the three previous releases were: Release 34, March 12, 2009 Release 33, January 20, 2009 Release 32, November 17, 2008 RefSeq is a free database for the public. |
| Content | not-present |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Generated Narrative: CodeSystem v3-refSeq
This case-sensitive code system http://www.ncbi.nlm.nih.gov/refseq defines codes, but no codes are represented here
FHIR{
"resourceType" : "CodeSystem",
"id" : "v3-refSeq",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: CodeSystem v3-refSeq</b></p><a name=\"v3-refSeq\"> </a><a name=\"hcv3-refSeq\"> </a><a name=\"v3-refSeq-en-US\"> </a><p>This case-sensitive code system <code>http://www.ncbi.nlm.nih.gov/refseq</code> defines codes, but no codes are represented here</p></div>"
},
"url" : "http://www.ncbi.nlm.nih.gov/refseq",
"identifier" : [
{
"system" : "urn:ietf:rfc:3986",
"value" : "urn:oid:2.16.840.1.113883.6.280"
}
],
"version" : "2.0.1",
"name" : "RefSeq",
"title" : "Gene Reference Sequence Collection",
"status" : "retired",
"experimental" : false,
"date" : "2021-11-09T10:00:00+10:00",
"publisher" : "NCBI",
"contact" : [
{
"name" : "National Center for Biotechnology Information,National Center for Biotechnology Information"
}
],
"description" : "The Reference Sequence (RefSeq) is one of the NCBI projects, the RefSeq collection aims to provide a comprehensive, integrated, non-redundant, well-annotated set of sequences, including genomic DNA, transcripts, and proteins. ReqSeq is accessible via BLAST, Entrez, and the NCBI FTP site. Information is also available in Entrez Genomes and Entrez Gene, and for some genomes additional information is available in the Map Viewer.\r\n\r\nRefSeq entries can be used with the HL7 coded data type. For example, in the HL7 messages specified according to the HL7 V2 Clinical Genomics Fully LOINC-Qualified Genetic Variation Model, RefSeq entries can be used to as the observation values for genomic reference sequence identifiers (LOINC \\#: 48013-7).\r\n\r\nMore information may be found at: http://www.ncbi.nlm.nih.gov/RefSeq\r\n\r\nVersioning informaiton: The latest release of RefSeq was released on May 13, 2009 with the release number of 35.\r\n\r\nRefSeq generates new releases roughly every two months. The dates of the three previous releases were: Release 34, March 12, 2009 Release 33, January 20, 2009 Release 32, November 17, 2008\r\n\r\nRefSeq is a free database for the public.",
"caseSensitive" : true,
"content" : "not-present"
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.